| Package | fhir.argonaut.scheduling |
| Type | CapabilityStatement |
| Id | Id |
| FHIR Version | R3 |
| Source | http://fhir.org/guides/argonaut/scheduling/https://simplifier.net/resolve?scope=fhir.argonaut.scheduling@1.0.0&canonical=http://fhir.org/guides/argonaut-scheduling/CapabilityStatement/client |
| Url | http://fhir.org/guides/argonaut-scheduling/CapabilityStatement/client |
| Version | 1.0.0 |
| Status | active |
| Date | 2018-03-18T18:00:00+11:00 |
| Name | Argonaut_Scheduling_Client_CapabilityStatement |
| Title | Argonaut Scheduling Client CapabilityStatement |
| Experimental | False |
| Realm | us |
| Authority | hl7 |
| Description | The Argonaut Scheduling Client CapabilityStatement provides a for a complete list of supported RESTful interactions for the Argonaut Scheduling Implementation Guide |
| Kind | requirements |
No resources found
| ImplementationGuide | |
http://fhir.org/guides/argonaut-scheduling/ImplementationGuide/ig  | Argo-Scheduling |
| http://fhir.org/guides/argonaut-scheduling/OperationDefinition/appointment-book | Appointment_Book |
| http://fhir.org/guides/argonaut-scheduling/OperationDefinition/appointment-find | Appointment_Availability_Operation |
| http://fhir.org/guides/argonaut-scheduling/OperationDefinition/appointment-hold | Appointment_Hold |
| http://fhir.org/guides/argonaut-scheduling/OperationDefinition/slot-prefetch | Availability_Prefetch_Operation |
Note: links and images are rebased to the (stated) source
This section outlines conformance requirements for the Argonaut Scheduling Client applications, identifying the specific profiles that need to be supported, the specific RESTful operations that need to be supported, and the search parameters that need to be supported. Note: The individual Argonaut Scheduling profiles identify the structural constraints, terminology bindings and invariants, however, implementers must refer to the conformance requirements for details on the RESTful operations, specific profiles and the search parameters applicable to each of the Argonaut Scheduling actors.
The Section describes the expected capabilities of the Argonaut Scheduling Scheduling Client which is responsible for creating and initiating the queries for information about patient scheduling as well as creating and updating this information. The complete list of FHIR profiles, RESTful operations, and search parameters supported by Argonaut Scheduling Servers are defined in the Argonaut Scheduling Server CapabilityStatement. Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.
Description:
The Argonaut Scheduling Client SHOULD:
The Argonaut Scheduling Client MAY:
For general security consideration refer to the Security section in the US Core Implementation Guide.
Specific server search capabilities are described in detail in each of the resource sections below.
Supported Profiles: Argonaut Appointment Profile
A client SHOULD be capable of fetching Appointments using:
GET [base]/Appointment/[id].
A client SHOULD be capable of fetching Appointments using search:
GET [base]/Appointment?patient=[id]{&status=[status]}{&date=[date]{&date=[date]}}{&practitioner=[id]}
A client SHOULD be capable of fetching Appointments by supporting the Appointment Availability Operation using either the GET or POST syntax.
GET [base]/Appointment/$find?{parameters}&?{_count}
POST [base]/Appointment/$find?{_count}
A client MAY be capable of creating or updating Appointments by supporting the Appointment Hold Operation.
POST [base]/Appointment/[id]/$hold
POST [base]/Appointment/$hold
A client SHOULD be capable of creating or updating Appointments by supporting the Appointment Book Operation.
POST [base]/Appointment/[id]/$hold
POST [base]/Appointment/$hold
A client SHOULD be capable of updating Appointments by supporting patch using either JSON, XML, or FHIRPath Patch.
PATCH [Base]/Appointment/[id]
Supported Profiles:
A client SHOULD be capable of consuming a Bundle as a response to a a query or operation.
Supported Profiles: Argonaut Coverage Profile
A client MAY be capable of updating or creating a patient's Coverage.
PUT [base]/Coverage/[id]
PUT or POST [base]/Coverage
Supported Profiles: US Core Patient Profile
A client SHOULD be capable of searching for Patients as defined in the US Core Implementation Guide.
A client MAY be capable of creating Patients by supporting create.
POST [base]/Patient
Supported Profiles: Argonaut Schedule Notification Profile
Supported Profiles: Argonaut Prefetch Slot Profile
A client MAY be capable of fetching Slots by supporting the Appointment Availability Operation.
Both the GET and POST Syntax SHALL be supported:
GET [base]/Slot/$prefetch?{parameters}
POST [base]/Slot/$prefetch
Supported Profiles: Argonaut Scheduling Subscription Profile
A client MAY be capable of creating Subscriptions
POST [base]/Subscription
A client MAY be capable of deleting Subscriptions
DELETE [base]/Subscription
FHIR{
"resourceType" : "CapabilityStatement",
"id" : "client",
"text" : {
"status" : "additional",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n\t\t\t<h2 id=\"argonaut-scheduling-conformance-requirements\">Argonaut Scheduling Conformance Requirements</h2>\n\t\t\t<p>This section outlines conformance requirements for the Argonaut Scheduling Client applications, identifying the specific profiles that need to be supported, the specific RESTful operations that need to be supported, and the search parameters that need to be supported. Note: The individual Argonaut Scheduling profiles identify the structural constraints, terminology bindings and invariants, however, implementers must refer to the conformance requirements for details on the RESTful operations, specific profiles and the search parameters applicable to each of the Argonaut Scheduling actors.</p>\n\t\t\t<h3 id=\"conformance-requirements-for-the-argonaut-scheduling-implementation-guide-client\">Conformance requirements for the Argonaut Scheduling Implementation Guide Client</h3>\n\t\t\t<ul>\n\t\t\t\t<li>FHIR Version: 3.0.1</li>\n\t\t\t\t<li>Supported formats: xml, json</li>\n\t\t\t\t<li>Published: March 20, 2018</li>\n\t\t\t\t<li>Published by: The Argonaut Project</li>\n\t\t\t</ul>\n\t\t\t<p>The Section describes the expected capabilities of the Argonaut Scheduling Scheduling Client which is responsible for creating and initiating the queries for information about patient scheduling as well as creating and updating this information. The complete list of FHIR profiles, RESTful operations, and search parameters supported by Argonaut Scheduling Servers are defined in the Argonaut Scheduling Server CapabilityStatement. Clients have the option of choosing from this list to access necessary data based on their local use cases and other contextual requirements.</p>\n\t\t\t<h4 id=\"behavior\">Behavior</h4>\n\t\t\t<p>Description:</p>\n\t\t\t<p>The Argonaut Scheduling Client <strong>SHOULD</strong>:</p>\n\t\t\t<ol>\n\t\t\t\t<li>Support fetching and querying scheduling information, using the supported RESTful interactions and search parameters declared in the Argonaut Scheduling Server CapabilityStatement.</li>\n\t\t\t\t<li>Conform to the <a href=\"http://hl7.org/fhir/us/core/1.0.1\">US Core Implementation Guide</a>.</li>\n\t\t\t</ol>\n\t\t\t<p>The Argonaut Scheduling Client <strong>MAY</strong>:</p>\n\t\t\t<ol>\n\t\t\t\t<li>Support creation and updates of scheduling and patient information, using the supported RESTful interactions and search parameters declared in the Argonaut Scheduling Server CapabilityStatement.</li>\n\t\t\t</ol>\n\t\t\t<h4 id=\"security-\">Security:</h4>\n\t\t\t<p>For general security consideration refer to the <a href=\"http://hl7.org/fhir/us/core/security.html\">Security section</a> in the US Core Implementation Guide.</p>\n\t\t\t<h4 id=\"profile-interaction-summary-\">Profile Interaction Summary:</h4>\n\t\t\t<p>Specific server search capabilities are described in detail in each of the resource sections below.</p>\n\t\t\t<h4 id=\"appointment\">Appointment</h4>\n\t\t\t<p>Supported Profiles: <a href=\"StructureDefinition-argo-appt.html\">Argonaut Appointment Profile</a>\n\t\t\t</p>\n\t\t\t<h5>Capabilities</h5>\n\t\t\t<ol>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of fetching Appointments using:</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>GET [base]/Appointment/[id]</code>.</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of fetching Appointments using search:</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>GET [base]/Appointment?patient=[id]{&status=[status]}{&date=[date]{&date=[date]}}{&practitioner=[id]}</code>\n\t\t\t\t\t</p>\n\t\t\t\t\t<ol>\n\t\t\t\t\t\t<li>A client <strong>SHOULD</strong> support the following search parameters:<ul>\n\t\t\t\t\t\t\t\t<li>_id</li>\n\t\t\t\t\t\t\t\t<li>patient</li>\n\t\t\t\t\t\t\t\t<li>status</li>\n\t\t\t\t\t\t\t\t<li>date - including the date modifiers ‘ge’,’le’,’gt’,’lt’</li>\n\t\t\t\t\t\t\t\t<li>practitioner</li>\n\t\t\t\t\t\t\t</ul>\n\t\t\t\t\t\t</li>\n\t\t\t\t\t</ol>\n\t\t\t\t</li>\n\t\t\t</ol>\n\t\t\t<ol>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of fetching Appointments by supporting the <a href=\"OperationDefinition-appointment-find.html\">Appointment Availability Operation</a> using either the <code>GET</code> or <code>POST</code> syntax.</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>GET [base]/Appointment/$find?{parameters}&?{_count}</code>\n\t\t\t\t\t</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Appointment/$find?{_count}</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>MAY</strong> be capable of creating or updating Appointments by supporting the <a href=\"OperationDefinition-appointment-hold.html\">Appointment Hold Operation</a>.</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Appointment/[id]/$hold</code>\n\t\t\t\t\t</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Appointment/$hold</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of creating or updating Appointments by supporting the <a href=\"OperationDefinition-appointment-book.html\">Appointment Book Operation</a>.</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Appointment/[id]/$hold</code>\n\t\t\t\t\t</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Appointment/$hold</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of updating Appointments by supporting patch using either JSON, XML, or FHIRPath Patch.</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>PATCH [Base]/Appointment/[id]</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t</ol>\n\t\t\t<hr/>\n\t\t\t<h4 id=\"bundle\">Bundle</h4>\n\t\t\t<p>Supported Profiles:</p>\n\t\t\t<ul>\n\t\t\t\t<li>\n\t\t\t\t\t<a href=\"StructureDefinition-avail-bundle.html\">Argonaut Appointment Bundle Profile</a>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<a href=\"StructureDefinition-slot-bundle.html\">Argonaut Slot Bundle Profile</a>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of consuming a Bundle as a response to a a query or operation.</p>\n\t\t\t\t</li>\n\t\t\t</ul>\n\t\t\t<h4 id=\"coverage\">Coverage</h4>\n\t\t\t<p>Supported Profiles: <a href=\"StructureDefinition-argo-coverage.html\">Argonaut Coverage Profile</a>\n\t\t\t</p>\n\t\t\t<h5>Capabilities</h5>\n\t\t\t<ol>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>MAY</strong> be capable of updating or creating a patient's Coverage.</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>PUT [base]/Coverage/[id]</code>\n\t\t\t\t\t</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>PUT or POST [base]/Coverage</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t</ol>\n\t\t\t<hr/>\n\t\t\t<h4 id=\"patient\">Patient</h4>\n\t\t\t<p>Supported Profiles: <a href=\"{{site.data.fhir.uscore}}/StructureDefinition-us-core-patient.html#search\">US Core Patient Profile</a>\n\t\t\t</p>\n\t\t\t<h5>Capabilities</h5>\n\t\t\t<ol>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>SHOULD</strong> be capable of searching for Patients as defined in the US Core Implementation Guide.</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>MAY</strong> be capable of creating Patients by supporting create.</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Patient</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t</ol>\n\t\t\t<hr/>\n\t\t\t<h4 id=\"schedule\">Schedule</h4>\n\t\t\t<p>Supported Profiles: <a href=\"StructureDefinition-argo-sched-notif.html\">Argonaut Schedule Notification Profile</a>\n\t\t\t</p>\n\t\t\t<ol>\n\t\t\t\t<li>A client <strong>MAY</strong> be capable of consuming a Schedule notification as a response to a <a href=\"StructureDefinition-argo-sub-notif.html\">Argonaut Scheduling Subscription Profile</a>.</li>\n\t\t\t</ol>\n\t\t\t<hr/>\n\t\t\t<h4>Slot</h4>\n\t\t\t<p>Supported Profiles: <a href=\"StructureDefinition-prefetch-slot.html\">Argonaut Prefetch Slot Profile</a>\n\t\t\t</p>\n\t\t\t<h5>Capabilities</h5>\n\t\t\t<ol>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>MAY</strong> be capable of fetching Slots by supporting the <a href=\"OperationDefinition-appointment-find.html\">Appointment Availability Operation</a>.</p>\n\t\t\t\t\t<ul>\n\t\t\t\t\t\t<li>\n\t\t\t\t\t\t\t<p>Both the <code>GET</code> and <code>POST</code> Syntax SHALL be supported:</p>\n\t\t\t\t\t\t\t<p>\n\t\t\t\t\t\t\t\t<code>GET [base]/Slot/$prefetch?{parameters}</code>\n\t\t\t\t\t\t\t</p>\n\t\t\t\t\t\t\t<p>\n\t\t\t\t\t\t\t\t<code>POST [base]/Slot/$prefetch</code>\n\t\t\t\t\t\t\t</p>\n\t\t\t\t\t\t</li>\n\t\t\t\t\t</ul>\n\t\t\t\t</li>\n\t\t\t</ol>\n\t\t\t<hr/>\n\t\t\t<h4 id=\"subscription\">Subscription</h4>\n\t\t\t<p>Supported Profiles: <a href=\"StructureDefinition-argo-sub-notif.html\">Argonaut Scheduling Subscription Profile</a>\n\t\t\t</p>\n\t\t\t<h5>Capabilities</h5>\n\t\t\t<ol>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>MAY</strong> be capable of creating Subscriptions</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>POST [base]/Subscription</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t\t<li>\n\t\t\t\t\t<p>A client <strong>MAY</strong> be capable of deleting Subscriptions</p>\n\t\t\t\t\t<p>\n\t\t\t\t\t\t<code>DELETE [base]/Subscription</code>\n\t\t\t\t\t</p>\n\t\t\t\t</li>\n\t\t\t</ol>\n\t\t</div>"
},
"url" : "http://fhir.org/guides/argonaut-scheduling/CapabilityStatement/client",
"version" : "1.0.0",
"name" : "Argonaut_Scheduling_Client_CapabilityStatement",
"title" : "Argonaut Scheduling Client CapabilityStatement",
"status" : "active",
"experimental" : false,
"date" : "2018-03-18T18:00:00+11:00",
"publisher" : "Argonaut Project",
"description" : "The Argonaut Scheduling Client CapabilityStatement provides a for a complete list of supported RESTful interactions for the Argonaut Scheduling Implementation Guide",
"jurisdiction" : [
{
"coding" : [
{
"system" : "urn:iso:std:iso:3166",
"code" : "US",
"display" : "United States of America"
}
]
}
],
"kind" : "requirements",
"fhirVersion" : "3.0.1",
"format" : [
"application/fhir+xml",
"application/fhir+json"
],
"patchFormat" : [
"application/json-patch+json",
"application/xml-patch+xml",
"application/fhirpath-patch+fhirpath"
],
"implementationGuide" : [
"http://fhir.org/guides/argonaut-scheduling/ImplementationGuide/ig",
"http://hl7.org/fhir/us/core/ImplementationGuide/ig"
],
"rest" : [
{
"mode" : "server",
"documentation" : "The [Argonaut](http://argonautwiki.hl7.org/) Scheduling Project is a vendor agnostic specification providing FHIR RESTful APIs and guidance for access to and booking of appointments for patients by both patient and practitioner end users. This specification is based on [FHIR Version 3.0.1]({{site.data.fhir.path}}) and specifically the [Scheduling and Appointment resources]({{site.data.fhir.path}}/administration-module.html#sched).",
"security" : {
"service" : [
{
"coding" : [
{
"system" : "http://hl7.org/fhir/restful-security-service",
"code" : "SMART-on-FHIR"
}
]
}
],
"description" : "For general security consideration refer to the [Security section](http://hl7.org/fhir/us/core/security.html) in the US Core Implementation Guide."
},
"resource" : [
{
"type" : "Appointment",
"interaction" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"code" : "read"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"code" : "search-type"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"code" : "patch"
}
],
"referencePolicy" : [
"enforced"
],
"searchParam" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "_id",
"definition" : "http://hl7.org/fhir/SearchParameter/_id",
"type" : "token"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "patient",
"definition" : "http://hl7.org/fhir/SearchParameter/patient",
"type" : "reference"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "status",
"definition" : "http://hl7.org/fhir/SearchParameter/status",
"type" : "token"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "date",
"definition" : "http://hl7.org/fhir/SearchParameter/date",
"type" : "date"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "practitioner",
"definition" : "http://hl7.org/fhir/SearchParameter/practitioner",
"type" : "reference",
"documentation" : "including the date modifiers ‘ge’,’le’,’gt’,’lt’"
}
]
},
{
"type" : "Coverage",
"interaction" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"code" : "create"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"code" : "update"
}
],
"updateCreate" : true,
"referencePolicy" : [
"enforced"
]
},
{
"type" : "Patient",
"documentation" : "A serve **SHALL** be capable of searching for Patients as defined in the US Core Implementation Guide",
"interaction" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"code" : "create"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"code" : "search-type"
}
],
"referencePolicy" : [
"enforced"
]
},
{
"type" : "Schedule",
"interaction" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"code" : "read"
}
]
},
{
"type" : "Subscription",
"interaction" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"code" : "create"
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"code" : "delete"
}
]
}
],
"operation" : [
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "find",
"definition" : {
"reference" : "http://fhir.org/guides/argonaut-scheduling/OperationDefinition/appointment-find"
}
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"name" : "hold",
"definition" : {
"reference" : "http://fhir.org/guides/argonaut-scheduling/OperationDefinition/appointment-hold"
}
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "SHOULD"
}
],
"name" : "book",
"definition" : {
"reference" : "http://fhir.org/guides/argonaut-scheduling/OperationDefinition/appointment-book"
}
},
{
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/capabilitystatement-expectation",
"valueCode" : "MAY"
}
],
"name" : "prefetch",
"definition" : {
"reference" : "http://fhir.org/guides/argonaut-scheduling/OperationDefinition/slot-prefetch"
}
}
]
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.